Ry's Git Tutorial: Defining Parallel Development Universes

In Git, parallel development is achieved through branching. Formally, a branch is an independent line of development that diverges from the main timeline. This allows multiple tracks of work to coexist as Internal Objects without interfering with the stability of the primary codebase.

1. The Primordial State: Master

Every repository begins with a default branch known as master. This is Git’s default branch. When you run git branch to list all branches, the asterisk (*) next to it indicates that it is the currently checked-out environment—your active universe.

2. The Feature Branch

While some branches are short-lived, a feature branch is a longer-running type of topic branch created with the specific intention of developing a specific feature. This isolates "work-in-progress" code from the production-ready "master" branch.

Analogy: Think of master blueprints for a skyscraper. To test solar panels, you use transparent overlays (feature branches). You can experiment and make mistakes on the overlays without ever risking the integrity of the original blueprints.

TERMINAL bash — 80x24

> Ready. Click "Run" to execute.

QUESTION 1

Which command is used to list all branches in a Git repository?

git list

git branch

git checkout --list

git show-branches

QUESTION 2

What does the asterisk (*) next to a branch name in the branch list signify?

The branch has uncommitted changes.

The branch is protected and cannot be deleted.

The branch is currently checked out (active).

The branch is the newest one created.

QUESTION 3

How is a 'feature branch' defined in Git development?

A branch that only contains CSS files.

A temporary branch that is never merged.

A longer-running topic branch for a specific functionality.

The branch where all bugs are fixed globally.

QUESTION 4

What is the name of Git's default development branch?

mainline

trunk

master

root

QUESTION 5

True or False: A branch is considered an 'internal object' that tracks specific changes.

True

False

Architectural Design Simulation

Managing Parallel Blueprints

You are leading a project to design a skyscraper. You have the 'master' blueprints finalized up to the 50th floor. Your client wants to see two options: a rooftop garden and a rooftop helipad. You decide to use Git branching logic to handle this request.

If you create a branch for the 'rooftop-garden', what happens to the 'master' blueprints while you work on the garden design?

Solution:
The master blueprints remain unchanged and stable. The garden design exists in an independent line of development, ensuring the original project history is not compromised.

Which specific branch type would the 'rooftop-garden' be categorized as?

Solution:
It would be a feature branch (or topic branch), created with the intention of developing a specific piece of functionality (the garden) in isolation.

How would you verify which 'blueprint' (branch) you are currently drawing on using the Git CLI?

Solution:
You would use the 'git branch' command. The branch name with the asterisk (*) next to it represents the currently checked-out environment.